E-mail messaging to/from a mobile terminal

ABSTRACT

Systems and methods for sharing an e-mail address between a host system ( 100 ) and a mobile terminal ( 102 ) addressable by a temporary wireless identity ( 122 D) in an access network ( 114 ). A terminal identifier ( 122 A) is assigned to the mobile terminal ( 102 ) or its user. The system comprises a connectivity function ( 600 ) and a messaging centre ( 110 ) that collectively maintain an association ( 610, 612 ) between the terminal identifier ( 122 A), encryption information ( 122 C) and the temporary wireless identity ( 122 D). When detecting an e-mail message addressed to the terminal identifier ( 122 A), the connectivity function encrypts the e-mail message with the encryption information ( 122 C). The messaging centre determines the temporary wireless identity ( 122 D) of the mobile terminal and transmits the encrypted e-mail message to the mobile terminal which receives and decrypts the encrypted e-mail message.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application relies for priority upon Finnish Application No.20045451, filed Nov. 22, 2004, and U.S. Provisional Application No.60/650,975, filed Feb. 9, 2005, the contents of both of which areincorporated herein by reference in their entireties.

BACKGROUND OF THE INVENTION

The invention relates to methods and equipment for transmittingelectronic mail (e-mail) messages to or from a mobile terminal.

U.S. Pat. No. 6,701,378 to Barry Gilhuly et al. discloses a system andmethod for pushing information, such as e-mail messages, from a hostsystem to a mobile data communication device (mobile terminal). Thetechnique permits e-mail processing at a mobile terminal in addition toa more stationary computer, referred to as a host system in the Gilhulypatent. Specifically, a redirector program operating at the host systemenables a user to continuously redirect certain user-selected data itemsfrom the host system to the user's mobile data communication device upondetecting that one or more user-defined triggering events has occurred.The redirector program operates in connection with event-generatingapplications and repackaging systems at the host system to configure anddetect a particular user-defined event, and then to repackage theuser-selected data items in an electronic wrapper prior to pushing thedata items to the mobile device. The mobile data communication devicemay originate new messages or reply messages to previously receivedinformation, such messages being transmitted to a wireless redirectorhost system, which then transmits a copy of the messages to both theintended recipient and a first electronic mail account associated withthe mobile data communication device.

The above-described prior art technique suffers from certainlimitations. For example, the host system, such as an office computer,and the mobile terminal require separate e-mail accounts. Some e-mailsystems support a .forward-type file for forwarding e-mail messages froma first e-mail account to a second e-mail account, but some systems donot support it. It is difficult to set up e-mail systems that do notsupport such forwarding techniques.

Furthermore, the Gilhuly patent does not address issues that relate tomanipulating e-mail messages at the second e-mail account (at the mobileterminal). For instance, it is difficult or impossible to use theterminal to arrange incoming e-mail messages into different folders atthe host system. Also, if the terminal user deletes an incoming e-mailmessage at the terminal, a copy of the deleted message is not present ina “deleted items” folder at the host system, which typically is the casein e-mail systems. Likewise, when the terminal sends an e-mail message,a copy of the message is not added to the host system's “sent items”folder. A further related problem is that e-mail messages that the userhas read at the terminal may appear as unread messages at the hostsystem.

Yet another problem is that configuring an e-mail client software at themobile terminal is difficult because of user interface restrictions intypical mobile terminals.

BRIEF DESCRIPTION OF THE INVENTION

An object of the present invention is to provide a method and anapparatus for implementing the method so as to integrate e-mailprocessing at the mobile terminal more seamlessly with the e-mailprocessing at the host system. In other words, the object of theinvention is to alleviate one or more of the disadvantages of the priorart.

The object of the invention is achieved by the methods and equipmentwhich are defined by the independent claims. The dependent claimsdisclose specific embodiments of the invention.

An advantage of the invention is more seamless integration of e-mailprocessing between the host system and the mobile terminal. For example,

-   -   provisioning of mobile e-mail is possible without affecting        e-mail configuration of the host system;    -   messages sent or deleted at the mobile terminal are        automatically moved to the respective folder at the host system,        ie, the “sent items” or “deleted items” folder.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following the invention will be described in greater detail bymeans of preferred embodiments with reference to the attached drawings,in which

FIG. 1 shows an exemplary system architecture in which the invention canbe used;

FIG. 2 shows provisioning of an e-mail system;

FIG. 3 shows a hypothetical scenario in which the e-mail system is used;

FIG. 4 shows information flows in mobile-terminated e-mail transmission;

FIG. 5 shows information flows in mobile-originated e-mail transmission;

FIG. 6 shows an enhanced embodiment in which some of the functions ofthe messaging centre are performed by a separate connectivity function;

FIG. 7 shows traffic flow in the embodiment shown in FIG. 6.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

FIG. 1 shows an exemplary system architecture in which the invention canbe used. Reference numeral 100 denotes a host system that is able tosend an receive e-mail messages. Reference numeral 102 denotes a mobileterminal, also able to send an receive e-mail messages. The e-mailmessages may originate or terminate at external e-mail terminals, one ofwhich is denoted by reference numeral 104. The invention aims atimproving cooperation between the host system 100 and mobile terminal102 such that they can use a single e-mail account as transparently aspossible. This means, for example, that the users of the external e-mailterminals 104, when sending or receiving e-mail, do not need to know ifthe user of the host system 100 actually uses the host system 100 or themobile terminal 102 to communicate via e-mail. The transparency alsomeans that e-mail manipulation at the mobile terminal 102 has, as far aspossible, the same effect as the corresponding e-mail manipulation atthe host system 100. For example, e-mail messages read at the mobileterminal 102 should preferably be marked as read at the host system.

Reference numeral 106 denotes a data network, such as an IP (InternetProtocol) network, which may be the common Internet or its closedsubnetworks, commonly called intranets or extranets. Reference numeral108 denotes an e-mail server and its associated database. The databasestores an e-mail account, addressable by means of an e-mail address,that appears as a mailbox to the owner of the e-mail account. In orderto communicate with mobile terminals 102, the data network 106 isconnected, via a gateway 112 to an access network 114. The accessnetwork comprises a set of base stations 116 to provide wirelesscoverage over a wireless interface 118 to the mobile terminals 102.

Reference numeral 110 denotes a messaging centre that is largelyresponsible for providing the above-mentioned transparency between thehost system 100 and the mobile terminal 102. The system architecturealso comprises a connectivity function, whose task is to push e-mailmessages to the mobile terminal. In the embodiment shown in FIG. 1, theconnectivity function is considered a physically integral but logicallydistinct element of the messaging centre 110. Later, in connection withFIGS. 6 and 7, an enhanced embodiment will be described that explicitlyassigns the security-related functions to the connectivity function andtraffic-related functions to the messaging centre 110.

The mobile terminal 102 may be a pocket or laptop computer with a radiointerface, a smart cellular telephone, or the like. Depending onimplementation, the host system 100, if present, may have differentroles. In some implementations the host system 100 is optional and maybe a conventional office computer that merely acts as the mobileterminal user's principal computer and e-mail terminal. In otherimplementations the host system may act as a platform for a singleuser's connectivity function, in addition to being an office computer.In yet other implementations the host system 100 may comprise theconnectivity function for several users. Thus it is a server instead ofa normal office computer.

We assume here that the access network 114 is able to establish andmaintain a tunnel 120 between the messaging centre 110 and the mobileterminal 102. For instance, the tunnel may be set up using GPRSTunnelling Protocol (GTP) or its later derivatives, or any othersuitable tunnelling protocol.

In a real system, there are naturally a large number of mobile terminals102 and tunnels 120. In order to keep track of which e-mail account andwhich tunnel belongs to which mobile terminal, the messaging centre 110maintains an association 122 for each mobile terminal supported by it.Each association 122 joins three fields, namely an e-mail address 122Aassigned to the mobile terminal or its user, encryption information 122Cand a temporary wireless identity 122D of the mobile terminal in theaccess network. The embodiment shown in FIG. 1 also employs a terminalidentifier 122B which may be the same as the e-mail address 122A of themobile terminal 102, in which case the association 122 actuallyassociates three information items. Alternatively, the terminalidentifier 122B may be an identifier arbitrarily assigned to the mobileterminal. In a preferred implementation the terminal identifier 122B isthe mobile terminal's equipment identifier or its derivative. Theencryption information 122C will be generated by the mobile terminal, asdescribed later in connection with FIG. 2. The temporary wirelessidentity 122D may be the identifier of the tunnel to the mobile station.Of course, the tunnel identifier is not permanent and is only known whena tunnel exists. The creation and use of the association 122 will befurther described in connection with FIGS. 2, 3 and 6.

FIG. 2 shows provisioning of an e-mail system in a system as shown inFIG. 1. The e-mail provisioning phase comprises the following steps. Ina preparatory step (not shown), appropriate e-mail software is installedin the host system 100 (if present) and mobile terminal 102, as well asin the e-mail server 108. For instance, the host system 100, the mobileterminal 102 and the e-mail server 108 may comprise and executeconventional e-mail software, such as Microsoft® Outlook, which may beaugmented by inventive client software that will be described in moredetail whenever necessary.

After the software installation, the next task is to create a securebinding between the connectivity function and the mobile terminal 102.The idea is to ensure that, in addition to the host system 100, only themobile terminal 102 used in the binding process can be used to accessand manipulate e-mail addressed to the mobile terminal's e-mail address.The binding operation faces two types of security risks. First, thecommunication used during binding must be secured against eavesdroppingor other types of hacking. Second, the only the user of the boundterminal 102 may access e-mail addressed to the e-mail address. Theeavesdropping problem is not trivial in a phase in which no trust existsbetween the mobile terminal 102 and the rest of the system. Yet anotherproblem is that the e-mail server 108 and the messaging centre 110typically have user interfaces that are only accessible to dedicatedsupport persons.

FIG. 2 shows a secure e-mail provisioning technique in which the hostsystem 100 authenticates the user of the mobile terminal 102. In step2-1 the client software in the mobile terminal 102 generates anddisplays a service activation code. In step 2-2 the host system 100authenticates the person who enters the service activation code. Insteadof a dedicated authentication step, the technique may rely on theauthentication of the underlying e-mail system, such as user name andpassword combination. After all, the e-mail provisioning need not bemore secure than the underlying e-mail system. In step 2-3 the serviceactivation code is then conveyed off-line to the host system 100. Theidea of the off-line communication is to eliminate any chance ofeavesdropping before secure a communication channel can be established.For instance, the service activation code may be entered manually or viaa local connection, such as a wired or optical interface or ashort-range wireless interface, such as Bluetooth™. Finally, in step2-4, the mobile terminal's service activation code is registered withthe connectivity function in the messaging centre 110.

The service activation code is closely related to an encryption key tobe used in future communications between the connectivity function inthe messaging centre 110 and the mobile terminal 102. The serviceactivation code and the encryption key may be identical, or one may be asubset of the other, or the encryption key may be derived from theservice activation code by means of some, preferably unpublished,algorithm. The fact that the service activation code and the encryptionkey are closely related to each other ensures that the terminal used inthe authentication process is the terminal used to access the e-mailservice afterwards.

Thus the idea of conveying the service activation code to the messagingcentre 110 via the host system 100 solves both the security-related anduser interface-related problems mentioned above. If there is no hostsystem 100 that can authenticate the mobile terminal and its user.Instead, the user may enter the provisioning data to the connectivityfunction via some suitable connection. The provisioning data entered bythe user may be checked by sending a trial e-mail message and attemptingto read it. If the check succeeds, it is regarded as the authentication.Yet another way is to convey the service activation code to a dedicatedsupport person who performs the authentication (eg by recognizing theperson's face or voice) and enters the service activation code into theconnectivity function in the messaging centre 110. The messagingcentre/connectivity function 110 now stores an association (item 122 inFIG. 1) between the e-mail address 122A and encryption information 122C.

FIG. 3 shows a hypothetical scenario in which the e-mail system is used.This scenario comprises four events, which are delineated by thickdashed lines. The first event, steps 3-10 through 3-16, relate toincoming e-mail. In step 3-10 the external e-mail terminal 104 sends ane-mail message to the e-mail server 108. The e-mail message is addressedto the user of the host system 100. Accordingly, a notification of theincoming e-mail is sent to the host system 100, but that step is omittedfrom FIG. 3 as purely conventional. In step 3-11 the mobile terminal 102requests the access network to establish a tunnel between itself and themessaging centre 110. Step 3-11 may take place before or after step3-10. After the tunnel establishment, the messaging centre 110 nowstores a complete association triplet (item 122 in FIG. 1) that joinsthe e-mail address 122A of the host system 100, the service activationcode 122C of the mobile terminal 102 and the tunnel identifier 122D ofthe tunnel to the mobile terminal 102.

In step 3-12 the messaging centre 110 detects and retrieves the incominge-mail from the e-mail server 108. For instance, the messaging centre110 may regularly poll the e-mail server 108 or it may register itselfas a listener to the e-mail server. In step 3-13 the messaging centre110 encrypts, and optionally packs, the e-mail message or parts of it.For instance, the messaging centre 110 may omit the destination addressof the e-mail message because it is self-evident that the e-mail messageis addressed to the user of the host system 100, who is also the user ofthe mobile terminal 102. The messaging centre 110 may also omit allattachments or large attachments, up to some threshold size, from thee-mail message to be conveyed to the mobile terminal. The encryptionprocess uses the mobile terminal's service activation code 122C, or itsderivative, as the encryption key. In step 3-14 the messaging centre 110transmits the encrypted and packed e-mail to the mobile terminal thatdecrypts and unpacks it in step 3-15. The messaging centre 110 knows thecorrect encryption key (service activation code) 122C and the tunnelidentifier 122D on the basis of the association triplet 122.

In step 3-16 the mobile terminal 102 sends the messaging centre 110 anautomatic control message indicating that the user has read the e-mailmessage. In response to the control message, the messaging centre 110signals the e-mail server 108 to mark the e-mail message as read in step3-17, which act the e-mail server performs in step 3-18. The controlmessage comprises some identification of the e-mail message but not itscontents, whereby it loads the radio interface only lightly. A benefitof the control message is that the user, when beginning to user the hostsystem 100, immediately sees which messages he/she has already read anddoes not have to read them twice.

Next in this scenario, the user decides that the e-mail message needsfurther attention when he/she is at the host system 100. The user mayinitiate another control message 3-22 that causes the previously readmessage to be marked as unread at the e-mail server in step 3-22.

The next phase, steps 3-30 through 3-34, relates to e-mail messagegeneration at the mobile terminal 102. We assume here, that the e-mailmessage to be generated is a reply message to the incoming messagedescribed above (steps 3-10 to 3-17), but the operation is very similarif the message to be generated is an original (non-reply) message. Instep 3-30 the mobile terminal user generates a reply message. Since itis a reply message, its recipient is automatically the sender of theincoming message, and the subject field comprises the original subjectwith a prefix of “RE:” or something similar. If the message is not areply message, the user will have to fill in the recipient and subjectfields. In step 3-31 the client software at the mobile terminal 102encrypts, and optionally packs, the outgoing e-mail message andtransmits it via the tunnel to the messaging centre 110. The messagingcentre 110 does not immediately know the sender of the e-mail message orthe required decryption key. But the messaging centre 110 does know theidentifier of the tunnel 120, and it employs the association triplet 122to retrieve the decryption key 122C and the mobile terminal user'se-mail address 122A. The latter is not included in the e-mail messagetransmitted over the wireless interface 118 in order to load thewireless interface as little as possible. In step 3-32, the messagingcentre 110 employs the decryption key 122C to decrypt the e-mailmessage. It also inserts the mobile terminal user's e-mail address 122A,which is the same as the host system's e-mail address because they sharethe same e-mail account. In step 3-33 the messaging centre 110 signalsthe e-mail server 108 to send a conventional reply message. In step 3-34the e-mail server 108 stores a copy of the message in its “sent items”folder. Because the messaging centre 110 signals the e-mail server 108to send a conventional reply message, the recipient of the message hasno way of knowing that the user actually used the mobile terminal toinitiate the message, and the desired transparency is achieved. Abenefit of the transparency is that when the external terminal 104 sendsa further reply, its user does not need to decide whether to send thereply to the host system or to the mobile terminal.

The final phase, steps 3-41 to 3-43, relate to deletion of an e-mailmessage. In response to the mobile terminal user's deletion command, themobile terminal 102 sends a control message in step 3-41 to themessaging centre 110. In step 3-42 it signals the e-mail server 108 todelete the message, and in step 3-43 the message is moved to the“deleted items” folder, again achieving complete transparency betweenthe host system and the mobile terminal.

As a further example of control messages, the user of the mobileterminal 102 may wish to explicitly move an e-mail message to aparticular folder. In this case the signalling is analogous to steps3-41 to 3-43, except that the message is not deleted but moved to adifferent folder. Only the control message has to be sent via thewireless interface, not the actual e-mail message.

FIG. 4 shows information flows in mobile-terminated e-mail transmission.Reference numeral 400 denotes an e-mail message as it appears on thefixed network side of the wireless interface 118. The e-mail message 400is sent by an external e-mail terminal 104 and processed by the hostsystem 100, the e-mail server 108 and/or the messaging centre 110. Forthe purposes of this description it comprises a source address field401, a destination address field 402, a subject field 403, a messagebody field 404 and, optionally, one or more attachments 405. There maybe other fields, such as cc (carbon copy) or bcc (blind carbon copy) butthey can be ignored in this discussion.

The messaging centre 110 comprises an encryption and packing logic 422that encrypts, and optionally packs (compresses), most of the fields ofthe e-mail message 400. However, the destination address field 402 isnot processed because the mobile terminal will generate it internally.The mobile terminal comprises a decryption and unpacking logic 424 whoseoperation is inverse to the encryption and packing logic 422.

It is also advantageous to implement a filtering logic 430 that filtersout attachments that exceed a threshold size, which is preferablyuser-settable. This means that the user is able to set an upper limitfor attachments that will be sent to the mobile terminal. Omittingattachments saves resources in the wireless interface and the mobileterminal. Instead of filtering long attachments, or in addition to it,the filtering logic 430 may be configured to cut out portions of ane-mail message body that exceeds a threshold size. Reference numeral 410denotes the e-mail message as received and processed by the mobileterminal. Instead of size-based filtering, or in addition to it, thefiltering logic may employ type-based filtering that filters outattachment types that the mobile terminal is not able to process. Forinstance, if the mobile terminal does not have a suitable codec forcertain types of video clips, it is pointless to send such video clipsto the mobile terminal.

FIG. 5 shows information flows in mobile-originated e-mail transmission.Reference numeral 500 denotes an e-mail message generated at the mobileterminal in response to a user input received via the terminal's userinterface. The e-mail message 500 is encrypted, and optionally packed,by an encryption and packing logic 522 that operates similarly to thelogic 422 in the messaging centre. Reference numeral 510 denotes thesame e-mail message after processing by a decryption and unpacking logic524 that reverses the encryption and packing by the logic 522.

The information flows in FIG. 5 are largely analogous to those in FIG.4, and a detailed description is omitted. However, in this direction thesource address, instead of the destination address, is omitted from thepacket sent over the wireless interface. In either direction, the e-mailaddress shared between the host system 100 and the mobile terminal 102is not transmitted over the wireless interface. Another difference toFIG. 4 is absence of the size/type-based filtering logic 430, because inmobile-originated messages the user can each time make the decisionwhether or not to include attachments.

FIG. 6 shows an enhanced embodiment in which some of the functions ofthe messaging centre are performed by a separate connectivity function.In the embodiments described so far the messaging centre 110 wasresponsible for data security issues and traffic coordination to/fromthe access network. In the embodiment shown in FIG. 6 a dedicatedconnectivity function 600 is responsible for the data security issues.FIG. 6 shows an arrangement in which the connectivity function 600 isphysically attached to or co-located with the messaging centre 110, butthey are logically separate elements. Indeed, a definite advantage ofthe separate connectivity function 600 is that it can be detached fromthe messaging centre, for instance, within the company that owns thehost system 100 or the e-mail server 108. For a small number of users,the connectivity function 600 can be installed in each host system 100,or the host system 100 can be interpreted as a separate serverconfigured to support multiple users. It is even possible to implementsome or all the above-mentioned options. This means, for example, thatthere is one or more messaging centres 110 that offer services toseveral network operators, or they may be a dedicated messaging centrefor each network operator (somewhat analogous to short messagingcentres). Each messaging centre 110 may have an integral connectivityfunction 600 to support users who don't wish to install a separateconnectivity function in a host system 100. For users who do install aseparate connectivity function 600 in their host systems 100, suchconnectivity functions bypass the connectivity function in the messagingcentre 110 and address the messaging centre 110 directly.

In the embodiment shown in FIGS. 1 to 3, the messaging centre maintainedan association 122 that joined the e-mail address 122A, terminalidentifier 122B (which may or may not be the same as the e-mailaddress), encryption information 122C and the temporary wirelessidentity 122D of the mobile terminal. In the embodiment shown in FIGS. 6and 7, the association is split into two, such that the connectivityfunction 600 maintains a first association 610 between the e-mailaddress 122A, terminal identifier 122B and the encryption information122C, while the messaging centre 110 maintains a second association 612between the terminal identifier 122B (or e-mail address 122A) and thetemporary wireless identity 122D of the mobile terminal. Thus in thisembodiment the messaging centre 110 does not know or need to know theencryption information 122C, which means that it only forwards trafficwithout being able to interpret it.

A further change caused by the separation (at least logical and,optionally, physical separation) of the connectivity function 600 fromthe messaging centre 110 is the fact that in step 2-4 of FIG. 2, themobile terminal's activation code (or any encryption information basedon it) is not delivered to the messaging centre 110 but to theconnectivity function 600.

FIG. 7 shows traffic flow in the embodiment shown in FIG. 6. Anextensive messaging scenario was described in connection with FIG. 3,and the description of FIG. 7 is restricted to the differences caused bythe separate connectivity function. In step 7-10, the e-mail server 108sends an incoming e-mail message to the connectivity function 600 (cf.steps 3-10 and 3-12 in FIG. 3). In step 7-11, the connectivity function600 encrypts, and optionally packs, the e-mail message. The packingcomprises one or more of the following: data compression, omission ofredundant fields, omission of long attachments and shortening messagebodies (cf. step 3-13 in FIG. 3 and items 422 and 430 in FIG. 4). Instep 7-12, the connectivity function 600 sends the encrypted and packede-mail message to the messaging centre 110. Up to this point, therecipient of the e-mail message has been identified based on the e-mailaddress 122A. In step 7-13, the messaging centre 110 forwards theencrypted and packed e-mail message via the access network to the mobileterminal, but in this step the recipient of the e-mail message isidentified based on the temporary wireless identity 122D of the mobileterminal. In step 7-14 the mobile terminal decrypts and unpacks thee-mail message. The unpacking comprises data decompression and/orregeneration of redundant fields (cf. step 3-15 in FIG. 3 and item 424in FIG. 4). Steps 7-20 through 7-25 relate to mobile-originated e-mailtransmission, and the steps performed are self-explanatory based on theabove descriptions.

As shown on the bottom row of FIG. 7, between the e-mail server 108 andthe connectivity function 600, traffic is identified based on the e-mailaddress 122A. Between the connectivity function 600 and the messagingcentre 110 traffic is identified based on the terminal identifier 122B.Finally, between the messaging centre 110 and the mobile terminal 102,traffic is identified based on the temporary wireless identity 122D,such as the tunnel identifier, TLLI or TMSI.

It is readily apparent to a person skilled in the art that, as thetechnology advances, the inventive concept can be implemented in variousways. The invention and its embodiments are not limited to the examplesdescribed above but may vary within the scope of the claims.

1. A system for forwarding an e-mail message, the system comprising: aconnectivity application executable by a processor in a data network to:detect the e-mail message at an e-mail server, encrypt at least part ofthe e-mail message, and send the encrypted e-mail message; and amessaging centre configured to receive the encrypted e-mail message fromthe connectivity application and to transmit the encrypted e-mailmessage via an access network to a mobile terminal for decryption, theaccess network establishing a tunnel between the messaging centre andthe mobile terminal, the mobile terminal having an e-mail address underthe e-mail server and a permanent terminal identity assigned to themobile terminal and a temporary identity in the access network, thetemporary identity based on an identifier of the tunnel to the mobileterminal.
 2. The system of claim 1, wherein the messaging centre isfurther configured to pack the at least part of the e-mail messagebefore transmission to the mobile terminal and to unpack the at leastpart of the e mail message after transmission to the mobile terminal. 3.The system of claim 2, wherein the messaging centre is furtherconfigured to pack the at least part of the e-mail message by omittingthe e-mail address.
 4. The system of claim 1, further comprising themobile terminal, the mobile terminal being configured to generateencryption information and to convey the encryption information via asecure channel to the connectivity application after authentication. 5.The system of claim 1, wherein the mobile terminal is further configuredto generate a control message relating to the e-mail message andindicating one of the following operations: marking the e-mail messageas read or unread or deleting the e-mail message and wherein the e-mailserver responds to the control message by marking the e-mail message asread or unread when the control message indicates marking the e-mailmessage as read or unread and moving the email message to a foldercontaining deleted e-mail messages when the control message indicatesdeleting the messages.
 6. The system of claim 1, wherein the messagingcentre is further configured to identify the e-mail message using thee-mail address the permanent terminal identity, and the temporaryidentity.